Allow non canonical values for Enums - #106
Merged
Merged
Conversation
azmeuk
force-pushed
the
34-no-canonical-values
branch
3 times, most recently
from
August 8, 2025 21:10
e546026 to
14e7bc4
Compare
RFC7643 §2.3.1 only allows service providers to restrict string attributes to their canonicalValues, so attributes suggesting canonical values now keep arbitrary values instead of rejecting them. This covers the type attribute of Email, PhoneNumber, Im, Photo, Address and AuthenticationScheme. Canonical values are matched case-insensitively, as §2.2 makes those attributes case-insensitive, and their JSON schema advertises the canonical values as examples instead of a restrictive enum.
azmeuk
force-pushed
the
34-no-canonical-values
branch
from
August 25, 2026 20:42
14e7bc4 to
f838368
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #34